I think it may be helpful if the order of the audio traffic warning information was in a different order.

At the moment the altitude of the "target" aircraft is announced last along with info if climbing, descending or level.

I had to listen to all the other info first before being able to decide if it is a likely threat or not.

If the warning info was re-ordered then SD users wouldn't have to listen to the whole warning before deciding if avoiding action was necessary.

Suggest the order is something like this:

Altitude (climbing/descending/level), position, crossing direction etc.

Tony

It was only a suggestion that, perhaps, having height (including climbing/level/descending) announced first would help SE2 users quickly be able to determine if an audio alert needed pilot action straight away. 

My particular SE2 "experience" was on the last good flying day before lockdown Mk2.

It was a very busy circuit at Sandown (approx. 5 aircraft arriving at the same time) and not only was I keeping a good visual lookout (and having to fly the circuit twice due to airfield operational issues) but I also received two warnings about an aircraft overtaking me at 330 Kt whilst I was overflying the airfield.

This sort of un-nerved me and only at the end out the audio announcement did I hear that the overtaking aircraft was at 35,000 ft!

That audio alert was a SD glitch (reported in a separate post) but was the trigger for this post.

Out of interest what do you think the negative aspects of SD announcing height etc. first in the audio alert would be?

Tony